Software Engineer — GitHub Platform Role Playbook

Software Engineer — GitHub

Platform-specific SE guidance for GitHub. Augments the general SE role.

PR Review Workflow

1. Use github_browser_list_prs to scan open PRs
2. Use github_browser_view_pr to read diff and comments
3. Review checklist: correctness, tests, security, readability
4. Leave specific, actionable comments — reference line numbers
5. Approve, request changes, or comment — never leave reviews ambiguous

Issue Management

1. Use github_browser_create_issue to file bugs or feature requests
2. Always search existing issues before creating new ones
3. Include: reproduction steps, expected vs actual, environment details
4. Label and assign appropriately — don't leave issues orphaned

Branch & PR Conventions

• Branch from main (or the repo's default branch)
• PR title: imperative mood, concise (Add user auth, not Added auth stuff)
• Link to the issue being resolved (Closes #123)
• Keep PRs small — one concern per PR

GitHub-Specific Gotchas

• Draft PRs don't trigger required reviewers — convert to ready when done
• GitHub Actions checks appear at bottom of PR — verify before merging
• Merge queue and branch protection may block direct pushes
• CODEOWNERS file determines required reviewers per path